-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unify building parts with their building #969
Conversation
The relation in the issue, the sf ferry building doesn't end up getting inserted into the database (it's in rels, but not in planet_osm_polygon). But, the outline does. This just means that currently the I also tried to find an example of a tile that had a |
@@ -151,7 +151,7 @@ Combination of OpenStreetMap administrative boundaries (zoom >= 8) and Natural E | |||
|
|||
Polygons from OpenStreetMap representing building footprint, building label_placement points, building_part features, and address points. Starts at zoom 13 by including huge buildings, progressively adding all buildings at zoom 16+. Address points are available at zoom 16+, but marked with `min_zoom: 17` to suggest that they are suitable for display at zoom level 17 and higher. | |||
|
|||
Individual `building:part` geometries from OSM following the [Simple 3D Buildings](http://wiki.openstreetmap.org/wiki/Simple_3D_Buildings) tags at higher zoom levels are now exported as `building_part` features with specified `kind_detail`. | |||
Individual `building:part` geometries from OSM following the [Simple 3D Buildings](http://wiki.openstreetmap.org/wiki/Simple_3D_Buildings) tags at higher zoom levels are now exported as `building_part` features with specified `kind_detail`. Building parts will receive a `root_id` that will correspond to the id of the `building` feature that they intersect. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pedantic, but: This makes it sound like building:part
s will always receive a root_id
, but its possible for building:part
s to not match any buildings
. Would it be clearer if it were written as follows?
Building parts may receive a
root_id
corresponding to thebuilding
feature, if any, with which they intersect.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call, updated in 3fa38ad.
Tile One pedantic thing: There are test cases for the non-overlapping and overlapping case, but none for the case where it picks the most overlapping of several candidates. Other than that, it looks great! 👍 |
Thanks. Updated in 8a6cb49. |
Added unit test for best overlap in aa7d144. |
👍 looks awesome! Nice work! |
1124614
to
bf06a5b
Compare
Connects to #653
@nvkelso, @zerebubuth could you review please?